Skip to content

Keep comms/ and research/ out of the built package - #235

Merged
NewGraphEnvironment merged 2 commits into
mainfrom
rbuildignore-internal-dirs
Aug 31, 2026
Merged

Keep comms/ and research/ out of the built package#235
NewGraphEnvironment merged 2 commits into
mainfrom
rbuildignore-internal-dirs

Conversation

@NewGraphEnvironment

Copy link
Copy Markdown
Owner

Summary

R CMD build ships every top-level directory not named in .Rbuildignore. link is an installable package, so pak::pak("NewGraphEnvironment/link") was putting internal cross-repo coordination notes (comms/) and research working files (research/) into the installer's library.

R CMD check reports this only as a NOTE, and .gitignore does not cover it.

Verification

Against the built tarball rather than the config, since the .Rbuildignore regex is easy to get subtly wrong:

comms/ research/
before 15 entries 22 entries
after 0 0

Why it was missed

planning, dev, .claude and CLAUDE.md were already excluded. comms/ and research/ were added to the repo later and never added to the ignore list — the gap opens over time rather than at scaffold.

This matters for the three-layer repo split: comms/ is internal by definition, so a package that flips public while shipping it leaks exactly what the flip was meant to purge.

Notes

Only .Rbuildignore is touched. The branch was cut from a working tree with 226 unrelated in-flight changes; none of them are staged or committed here.

Convention entry and an audit loop covering the other repos: NewGraphEnvironment/soul#60

🤖 Generated with Claude Code

https://claude.ai/code/session_01EPc4Xkk81mE4JHuP5A1SnS

`R CMD build` ships every top-level directory not named in `.Rbuildignore`,
so `pak::pak("NewGraphEnvironment/link")` was putting internal cross-repo
coordination notes and research working files into the installer's library.
`R CMD check` reports this only as a NOTE, and `.gitignore` does not cover it.

Verified against the tarball rather than the config: 37 `comms/` + `research/`
entries before, 0 after.

`planning`, `dev`, `.claude` and `CLAUDE.md` were already excluded - these two
were added later and missed. Convention and an audit loop for the other repos
are in NewGraphEnvironment/soul#60.

Co-Authored-By: Claude <[email protected]>
Claude-Session: https://claude.ai/code/session_01EPc4Xkk81mE4JHuP5A1SnS
…ind)

* main: (43 commits)
  Pack components by finish time, not segment count
  Fix two pre-flight gates the first real pilot exposed (v0.47.1)
  Fail loudly when a fresh cypher never accepts a connection
  Assert per-host drainage closure and DS-first order (#246)
  code-check round 5 clean; sweep the last two unsafe greps (#246)
  code-check round 4: the empty-bucket guards could never run (#246)
  code-check round 3: stop the completeness gate destroying good work (#246)
  code-check round 2: fix a blocker inside round 1's fix (#246)
  code-check round 1: fix the TSV seam and four fragile spots (#246)
  Phase 4: RUNBOOK section 8d, NEWS, v0.47.0
  Phase 3: derive the host buckets instead of asserting them (#246)
  Phase 2: pre-flight gates for the study-area run (#246, absorbs #183)
  Phase 1: make fresh a real dependency; fix the prep sentinel (#246)
  Initialize PWF baseline for #246
  CLAUDE.md: sync version header to v0.46.0 (memory-audit, soul#47)
  Update CLAUDE.md with soul conventions
  Archive planning files for issue #227
  Wrap long lines in the guard message builder (#227)
  Phase 5 (#227): RUNBOOK 8c, guard-note docs, CLAUDE.md status, release v0.46.0
  Phases 3-4 (#227): wire the guard into the runners, add the post-condition
  ...
@NewGraphEnvironment

NewGraphEnvironment commented Aug 31, 2026

Copy link
Copy Markdown
Owner Author

Updated the branch before merging: it was 55 commits behind main and its .claude/settings.local.json was a 2026-08-01 snapshot that would have reverted the permission allowlist from 35 entries to 5. The body's claim that "only .Rbuildignore is touched" was accurate when written and had quietly stopped being true.

Merged main in; the branch's delta vs main is now exactly the 2 lines it describes, and settings match main.

Re-measured the tarball rather than trusting the month-old table — research/ has grown since (a generated study_areas.md landed today):

comms/ research/
before 15 22
after 0 0

Same result, current evidence. (Corrected: an earlier revision of this comment mistyped the research/ before-count as 15.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant